I recently built a SCOM 2007 R2 environment in my personal lab. I have 4 Windows Server 2008 boxes with various workloads running (Exchange 2007, SQL, WSUS, etc). After installing and configuring SCOM, I installed only the core Windows Server management packs and then I addressed the alerts that it generated. It's been running for about a week with no new alerts, so last night I installed the Exchange 2007 MP. When I opened the console this morning I noticed that my Exchange server had not been discovered, and I have a "PowerShell Script failed to run" alert. The alert details are: "System.Management.Automation.MethodInvocationException: Exception calling "Connect" with "1" argument(s): The user xxx\xxx does not have sufficient permission to perform the operation. Script Name: DiscoverTargetRelationshipOne or more workflows were affected by this. Workflow name: Microsoft.Exchange2007.Rms.TargetRelationship.Discovery" The account being referenced is my action account, which is in my Domain Admins group. Are there some additional rights that I need to grant to the action account in order for MP's to be able to discover systems?

Hi Jason Do the domain admins have read access to Exchange? It is quite normal for example for SQL servers to have the local admins gorup and the domain admins removed You need to make sure your action account has exchange permissions and that the discoveries are enabled (by default all Exchange discoveries are dissabled by default!) Let me know how you are getting on Paul Paul Keely

When I opened the console this morning I noticed that my Exchange server had not been discovered, and I have a "PowerShell Script failed to run" Is it the PowerShell execution policy that is blocking this script?Regards, Marc Klaver http://jama00.wordpress.com/

Thanks for the help. I failed to read the MP deployment guide first (RTFM, eh?) and once I did, I realized that I hadn't enabled discovery. So I did that yesterday, and I cleared the PowerShell alert. When I opened the console this morning I noticed that my Exchange environment has now been discovered, but the PowerShell alert is back. I have not, however, granted Exchange permissions to the action account so I'll do that now and close the PowerShell alert again and then see what happens. Thanks. Jason

Hey Jason The one MP that needs to be read is the Exchange MP.. It will do you all the good in the world to go over it a few times. Have you run the new testcasconnectivityuser (or whatever its called..) Once its run the MP is a joy to work with. It really only works fully in my opioion if you use an edge server... Let me know if I can help any Paul Paul Keely

OK so this problem hasn't gone away. My action account is a domain admin, has logon as a service rights, and is an Exchange admin. However I'm still getting the PowerShell script failure error (noted in my original post). I've read through the Exchange MP deployment guide and I thought I caught everything. Object discovery is enabled and my Exchange environment is being discovered. Marc mention a PowerShell execution policy. Is there something that I need to do in order to allow PowerShell scripts to run? Jason

Hi Jason Is this still an issue? I have come across this post in the past where this error is generated when just the Exchange Management Console is installed but no Exchange role. I realise it is a long shot but is that the case here? http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/24587/Default.aspx The Exchange 2007 Management Pack does include servers with the Exchange Management Console installed as Exchange Servers: http://systemcentersolutions.wordpress.com/2009/07/09/exchange-2007-discoveries-2/ Good Luck GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Hi Graham, thanks for checking in and apologize for the delay. Yes, this is still an issue. The source server is showing as my SCOM server, which does not have the Exchange management console (or any Exchange services for that matter). As I mentioned above, the action account is the one noted in the error as not having sufficient permission to perform the operation, but that account is a domain admin, Exchange admin, and has logon as a service rights. Marc mentioned something about a PowerShell execution policy that could be blocking the script. Do you know what this is and how I can troubleshoot this? Jason

Did you solve this? I'm having the exact same problem, unable to find a solution to it. Anders

Did you solve this? I'm having the exact same problem, unable to find a solution to it. Anders No, I never did solve this. This was a lab environment and I ended up re-paving the lab (not because of this issue, I just had different requirements and needed to build the lab differently)

Did you solve this? I'm having the exact same problem, unable to find a solution to it. Anders No, I never did solve this. This was a lab environment and I ended up re-paving the lab (not because of this issue, I just had different requirements and needed to build the lab differently)